home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970326-19970626
/
000008_news@columbia.edu _Fri Mar 28 13:40:57 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
5KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id NAA04577
for <kermit.misc@watsun.cc.columbia.edu>; Fri, 28 Mar 1997 13:40:56 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id NAA06934
for kermit.misc@watsun; Fri, 28 Mar 1997 13:40:54 -0500 (EST)
Path: news.columbia.edu!panix!news.mathworks.com!enews.sgi.com!news.corp.sgi.com!news.sgi.com!news1.best.com!news.impulse.net!stephen
From: stephen@arktel.com (Stephen Au)
Newsgroups: comp.os.ms-windows.nt.misc,comp.protocols.kermit.misc
Subject: Re: K95 Kermit flickers on Key Input in NT4.0
Date: 28 Mar 1997 18:33:52 GMT
Organization: Impulse Internet Sevices
Lines: 85
Message-ID: <5hh2ug$e5p$1@news.impulse.net>
References: <5hbo8d$lbi$1@news.impulse.net> <5hc84u$qum@watsun.cc.columbia.edu>
Reply-To: stephen@arktel.com
NNTP-Posting-Host: 204.188.4.81
X-Newsreader: slrn (0.9.3.2 OS/2)
Xref: news.columbia.edu comp.os.ms-windows.nt.misc:185142 comp.protocols.kermit.misc:6823
>Frank da Cruz wrote:
>>In article <5hbo8d$lbi$1@news.impulse.net>,
>>Stephen Au <stephen@arktel.com> wrote:
>>:
>>: I have been using K95 under WIN95 for sometime and it works OK (slow)
>>:
>>Slow compared to what?
>>
Slow in couple respects, with serial connections @ 9600/19200 bps.
#1. Compared to real-life WYSE-60 terminals at 9600/19200 bps.
*All* 5 users of K95 on WIN95
reported K95 as slow compared to their terminals. And these are all
Pentium 75 with 16MB machines and all they are doing is connecting to Unix.
I tuned the "SET TERMINAL SCREEN-UPDATE FAST" and that improves some but
still no compairson with the WYSE in terms of scrolling speed.
People performing similar jobs on
a WYSE and then on K95 consistently reported the WYSE as getting their
job done faster. BTW these users are accountants, they are not anti-computers,
and they love their PCs much more than the WYSE.
I grant that this
"perception" of "slowness" is largely due to the pausing between screen updates
because I timed the output with a stop watch and the result is similar.
But on keyboard input, there is just this perceptible delay between
a key is depressed and a character appearing on the screen.
And it slows down productivity.
#2. Compared with other versions of Kermit, notably MSDOS and OS2/Warp 4.
It takes longer for K95 to come up and exit, K95 feels sluggish/unresponsive
on keyboard input. (And the "perception of slowness" on output).
#3. Compared with Qmodem.
It takes longer for K95 to come up and exit, K95 feels sluggish/unresponsive
on keyboard input.
So why do I use and recommend K95? Because it does SCOANSI, and because
I was sold on the MSDOS and OS2 versions. Just consider these as end-users
comments.
>>: and I can't use just any window size I want.
>>:
>>Due to a bug in Windows 95.
>>
That was a major reason why I upgrade to NT.
>>
>>: Does anyone has similar problem and has a remedy? Thank you very much.
>>:
>>Some people have seen this, most do not see it.
>>
>>In Windows, we're dealing with a much more... "complicated" environment.
>>There are infinite combinations of hardware, graphics adapters, drivers,
>>BIOS's, etc, and bugs in all of these.
>>
I would think that this is a step forward than the old days of pure DOS,
with Windows and WIN drivers to give some isolation from raw iron.
>>Kermit is updating the screen in the approved Win32 manner. If there is
>>flicker, it is not caused by Kermit, but rather by the driver that Kermit
>>is calling upon to do it, and/or the video adapter.
>>
>>The following entry from Kermit 95's BUGS.TXT file might be helpful:
>>
>> .....
>>
Thank you for the info, and I have read that, and those suggestions
did not fix the problem. What gets me is that this
flicker *does not* happen with a vanilla NT MSDOS window.
It does not happen with other screen-oriented applications such as
"vi" (MKS version), "vim" (NT or WIN32), "brief" (DOS mode).
And K95 is doing it "the approved Win32 manner".
For a silly consumer like me, this is very disappointing.
FWIW, I love Kermit/WARP4 and I use it everyday. Kermit is the single
most important application that I use. I understand that K95 is moving
toward GUI and I don't see the need to go GUI for a comm, terminal-emulation
program to do that, unless X is in the cards, as long as there is mouse
support which is quite good already.